• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    SYSTEM AND METHODS TO MAINTAIN CORE NETWORK STATE DURING RELOCATION OF SERVER RADIO NETWORK SUBSYSTEM. A system and method allows the wireless UE to undergo server SRNS reallocation to an RNC that does not support a fast dormancy feature while maintaining synchronization with the core network packet-swapped domain. The UE is advised of whether the target RNC supports the fast dormancy feature by means of an indication provided to the UE in a reconfiguration message provided by the source RNC, that is, the RNC to which the UE was connected prior to the SRNS relocation. In this way, the UE can behave accordingly whether or not the target RNC supports and fast domain feature.
    公开号:BR112012003056B1
    申请号:R112012003056-6
    申请日:2010-08-11
    公开日:2021-04-20
    发明作者:Kiran Kishanrao Patil；Liangchi Hsu；Rohit Kapoor；Sharad Deepak Sambhwani；Aziz Gholmieh
    申请人:Qualcomm Incorporated；
    IPC主号:
    专利说明:

    Cross Reference to Related Orders
    [0001] This application claims the benefits of provisional patent application US No. 61/233,043 entitled "SYSTEMS AND METHODS OF MAINTAINING CORE NETWORK STATUS DURING SERVING RADIO NETWORK SUBSYSTEM RELOCATION", filed on August 11, 2009, the description of which is expressly incorporated herein by reference in its entirety. Fundamentals Field
    [0002] Aspects of the present description relate generally to wireless communication systems and more particularly to techniques for improving battery life in wireless mobile devices by allowing them to enter a sleep or idle mode. Fundamentals
    [0003] Wireless communication networks are widely developed to provide various communication services such as telephony, video, data, messaging, broadcast and so on. Such networks, which are normally multiple access networks, support communications for multiple users by sharing available network resources. An example of such a network is the UMTS Terrestrial Radio Access Network (UTRAN). UTRAN is the radio access network (RAN) defined as part of the Universal Mobile Telecommunications System (UMTS), a third generation (3G) mobile telephony technology supported by the 3rd Partnership Project. Generation (3GPP). UMTS, which is the successor to the Global System for Mobile Communications (GSM), currently supports several air interface standards such as Broadband Code Division Multiple Access (W-CDMA), Code Division Multiple Access, and Code Division Multiple Access Time (TD-CDMA), and Time Division Synchronized Code Division Multiple Access (TD-SCDMA). UMTS also supports enhanced 3G data communication protocols, such as High Speed Packet Access (HSDPA), which provide higher data transfer speeds and associated UMTS network capacity.
    [0004] As demand for mobile broadband access continues to grow, research and development continues to advance UMTS technologies not only to meet the growing demand for mobile broadband access, but to advance and improve the user experience. user with mobile communications. summary
    [0005] In one aspect of the description, a wireless communication method includes receiving a notification to relocate a source server radio network (SRNS) subsystem to a target SRNS and determining whether a target radio network controller ( RNC) corresponding to the target SRNS supports a fast dormancy feature. If the target RNC supports the fast sleep feature, the user equipment (UE) can enter a sleep state, power-saving state, or idle state to save battery life.
    [0006] In an aspect of the description, an apparatus for wireless communication includes means for receiving a notification for relocating from a source SRNS to a target SRNS, and means for determining whether a target RNC corresponding to the target SRNS supports a fast dormancy feature . If the target RNC supports the fast sleep feature, the UE includes means of entering a dormant state, power saving state or idle state to save battery life.
    [0007] In one aspect of the description, a computer program product includes a computer-readable medium having a code for receiving a notification to relocate from a source SRNS to a target SRNS, and to determine whether a target RNC matches the target SRNS supports a fast dormancy feature. If the target RNC supports the fast sleep feature, the computer-readable medium has a code to enter a sleep state, power save state, or idle state.
    [0008] In an aspect of the description, an equipment for wireless communication includes at least one processor and a memory coupled to at least one processor. Here, the at least one processor is configured to receive a notification to relocate from a source SRNS to a target SRNS, and to determine whether a target RNC corresponding to the target SRNS supports a fast dormancy feature. If the target RNC supports the fast sleep feature, the processor is configured to enter a sleep state, power save state, or sleep state.
    [0009] These and other aspects of the invention will become more fully understood upon review of the detailed description that follows. Brief Description of Drawings
    [0010] Figure 1 is a diagram illustrating an example of a hardware implementation for an equipment employing a processing system;
    [0011] Figure 2 is a block diagram conceptually illustrating an example of a telecommunications system;
    [0012] Figure 3 is a conceptual diagram illustrating an example of an access network;
    [0013] Figure 4 is a block diagram conceptually illustrating an example of a Node B in communication with a UE in a telecommunications system;
    [0014] Figure 5 is a call flowchart conceptually illustrating a UE and an RNC that does not support the fast sleep feature out of sync in the prior art;
    [0015] Figure 6 is a flowchart illustrating a process of maintaining synchronization between a UE and an RNC after a reallocation of SRNS in case the RNC supports the fast dormancy feature or not;
    [0016] Figure 7 is a conceptual block diagram conceptually illustrating illustrative blocks performed to implement the functional characteristics of an aspect of the present description. Detailed Description
    [0017] The detailed description presented below with respect to the attached drawings is intended to serve as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing an in-depth understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without the specifics. In some cases, well-known structures and components are illustrated in block diagram form in order to avoid obscuring such concepts.
    [0018] Various aspects of telecommunications systems will now be presented with reference to the various equipment and methods. These equipment and methods will be described in the detailed description below and illustrated in the attached drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and the design constraints imposed on the system as a whole.
    [0019] By way of example, an element, or any part of an element, or any combination of elements can be implemented with a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate assemblies (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various features described throughout this description. One or more processors in the processing system may run the software. Software shall be broadly constructed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable elements, execution sequences, procedures, functions, etc. referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer-readable medium. A computer-readable medium may include, by way of example, a magnetic storage device (eg, hard disk, floppy disk, magnetic stripe), an optical disk (eg, compact disk (CD), digital versatile disk (DVD) ), a smart card, a flash memory device (eg card, stick, key drive), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM) , electrically erasable PROM (EEPROM), record, removable disk, carrier wave, transmission line or any other suitable medium for storing or transmitting software. The computer-readable medium may be resident in the processing system external to the processing system, or distributed across multiple entities including the processing system. The computer-readable medium can be embodied in a computer program product. By way of example, a computer program product can include a computer readable medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this description depending on the particular application and general design constraints imposed on the system as a whole.
    [0020] Figure 1 is a conceptual diagram illustrating an example of a hardware implementation for an equipment 100 employing a processing system 114. In this example, the processing system 114 can be implemented with a bus architecture, generally represented by the bus 102. Bus 102 may include any number of interconnecting buses and bridges depending on the specific application of processing system 114 and general design constraints. Bus 102 connects various circuits including one or more processors, generally represented by processor 104, and computer readable media, generally represented by computer readable medium 106. Bus 102 may also connect various other circuits such as timing sources, peripherals , voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described further. A bus interface 108 provides an interface between the bus 102 and a transceiver 110. The transceiver 110 provides a means of communicating with various other equipment via a transmission medium. Depending on the nature of the equipment, a 112 user interface (eg keyboard, monitor, speaker, microphone, joystick) may also be provided.
    [0021] Processor 104 is responsible for managing the bus 102 and general processing, including the execution of software stored on the computer-readable medium 106. The software, when executed by the processor 104, causes the processing system 114 to perform the various functions described below for any particular equipment. Computer readable medium 106 can also be used to store data that is manipulated by processor 104 when running the software.
    [0022] The various concepts presented throughout this description can be implemented through a wide variety of telecommunication systems, network architectures, and communication standards. By way of example and without limitation, aspects of the present description illustrated in Figure 2 are presented with reference to a UMTS 200 system employing a W-CDMA air interface. A UMTS network includes three interaction domains: a Core Network (CN) 204, a UTRAN 202, and a UE 210. In this example, the UTRAN 202 provides various wireless services including telephony, video, data, messaging, broadcasts and/or other services. The UTRAN 202 may include a plurality of Serving Radio Network Subsystems (SRNSs) such as an SRNS 207, each controlled by a respective RNC such as an RNC 206. Here, UTRAN 202 may include any number of RNCs 206 and SRNSs 207 in addition to the RNCs 206 and SRNSs 207 illustrated here. The RNC 206 is equipment responsible for, among other things, assignment, reconfiguration, and release of radio resources within the SRNS 207. The RNC 206 can be interconnected with other RNCs (not shown) in the UTRAN 202 through various types of interfaces such as a direct physical connection, a virtual network, or the like, using any suitable transport network.
    [0023] The geographic region covered by the SRNS 207 can be divided into a number of cells, with a radio transceiver equipment serving each cell. A radio transceiver equipment is commonly referred to as a Node B in UMTS applications, but may also be referred to by those skilled in the art as a base station (BS), a base transceiver station (BTS), a radio base station, a transceiver a radio, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), or some other suitable terminology. For clarity, three Node B 208 are illustrated in each SRNS 207; however, SRNSs 207 can include any number of wireless Node Bs. Node B 208 provides wireless access points to a CN 204 for any number of mobile devices. Examples of a mobile device include a cell phone, a smart phone, a session initiation protocol (SIP) phone, laptop, notebook, netbook, smartbook, a personal digital assistant (PDA), a satellite radio, a computer device. global positioning system (GPS), a multimedia device, a video device, a digital audio equipment (eg, MP3 equipment), a camera, a game console, or any other similarly functioning device. Mobile equipment is commonly referred to as UE in UMTS applications, but may also be reflected by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a unit remote, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a equipment, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. In a UMTS system, the UE 210 may additionally include a universal subscriber identity module (USIM) 211, which contains a user subscription information for a network. For illustration purposes, a UE 210 is illustrated in communication with a number of Node Bs 208. Downlink (DL), also called forward link, refers to the communication link from a Node B 208 to a UE 210, and uplink (UL), also called reverse link, refers to the communication link from a UE 210 to a Node B 208.
    The CN 204 domain interfaces with one or more access networks, such as the UTRAN 202. As illustrated, the core network 204 is a GSM core network. However, as those skilled in the art will recognize, the various aspects presented throughout this description can be implemented in a RAN, or other suitable access network, to provide UEs with access to core network types other than GSM networks.
    [0025] The core network 204 includes a circuit-switched domain (CS) and a packet-switched domain (PS). Some of the circuit-swapped elements are a Mobile Services Exchange Center (MSC), Visitor Location Record (VLR) and an Access Circuit MSC. Packet-swapped elements include a Server GPRS Support Node (SGSN) and an Access Circuit GPRS Support Node (GGSN). Some network elements such as EIR, HLR, VLR and AuC can be shared by both circuit-swapped or packet-swapped domains. In the illustrated example, the core network 204 supports circuit-switched services with an MSC 212 and a GMSC 214. In some applications, the GMSC 214 may be referred to as a media access circuit (MGW). One or more RNCs, such as the RNC 206, can be connected to the MSC 212. The MSC 212 is equipment that controls call setup, call forwarding and UE mobility functions. The MSC 212 also includes a VLR that contains subscriber related information for the length of time the UE is in the coverage area of the MSC 212. The GMSC 214 provides an access circuit through the MSC 212 for the UE to access a swapped network per circuit 216. The GMSC 214 includes an HLR 215 containing subscriber data, such as data reflecting details of the services to which a particular user is subscribed. The HLR is also associated with an AuC that contains subscriber-specific authentication data. When a call is received for a particular UE, the GMSC 214 polls the HLR 215 to determine the location of the UE and forward the call to the particular MSC serving that location.
    [0026] The core network 204 also supports packet data services with an SGSN 218 and a GGSN 220. GPRS, which stands for General Packet Radio Service, is designed to provide packet data services at higher speeds. than those available with GSM circuit-switched data services. GGSN 220 provides a connection to the RAN 202 for a packet-based network 222. The packet-based network 222 can be the Internet, a private data network, or some other suitable packet-based network. The primary function of the GGSN 220 is to provide the UEs 210 with packet-based network connectivity. Data packets are transferred between the GGSN 220 and the UEs 210 through the SGSN 218, which performs basically the same functions in the packet-based domain as the MSC 212 performs in the circuit-swapped domain.
    [0027] The UMTs air interface is a Direct Sequence Code Division Multiple Access and spread spectrum (DS-CDMA) system. Spread-spectrum DS-CDMA spreads user data across a much larger bandwidth by multiplying by a sequence of pseudo-random bits called chips. The W-CDMA air interface is based on such direct sequence spread spectrum technology and additionally requires frequency division duplexing (FDD). FDD uses a different carrier frequency for UL and DL between a Node B 208 and a UE 210.
    [0028] Referring to Fig. 3, an access network 300 in a UTRAN architecture is illustrated. The multi-access wireless communication system includes multiple cellular regions (cells), including cells 302, 304, and 306, each of which may include one or more sectors. The multiple sectors can be formed by groups of antennas with each antenna being responsible for communicating with the UEs in one part of the cell. For example, in cell 302, antenna groups 312, 314, and 316 can each correspond to a different sector. In cell 304, antenna groups 318, 320, and 322 each correspond to a different sector. In cell 306, antenna groups 324, 326, and 328 each correspond to a different sector. Cells 302, 304, and 306 may include a number of wireless communication devices, e.g. UEs, which may be in communication with one or more sectors of each cell 302, 304, or 306. For example, UEs 330 and 332 may be in communication with Node B 342, UEs 334 and 336 can be in communication with Node B 344, and UEs 338 and 340 can be in communication with Node B 346. Here, each Node B 342, 344, 346 is configured to provide an access point for a core network 204 (see figure 2) for all UEs 330, 332, 334, 336, 338, 340, in respective cells 302, 304 and 306.
    [0029] In one example, the UMTS signaling protocol stack can be divided into Access Extract (AS) and Non-Access Extract (NAS). NAS is a functional layer between the UE and the core network, managing the functions and services that are independent of the access technology. AS supports NAS by managing functions and protocols for transporting information over the UTRAN and the air interface.
    [0030] NAS may include a Connection Management unit to handle circuit-switched calls, and may include sublayers responsible for call control (e.g. establishment, release), supplementary services (e.g. call forwarding, call with three people), and short message services (SMS). NAS may additionally include a Session Management unit to handle packet exchanged calls (eg set up, release). NAS may additionally include a Mobility Management module to handle location updating and authentication for circuit-switched calls. NAS may additionally include a GPRS mobility management unit to handle location updating and authentication for packet exchanged calls.
    [0031] Likewise, AS may include a Radio Resource Control unit (RRC) having protocols that are defined between the UE and the RNC to handle the establishment, release and configuration of radio resources. AS may additionally include an RLC unit having protocols that are defined between the UE and the RNC to provide segmentation, reassembly, duplication detection, and other traditional Layer 2 functions. AS may further include a Media Access Control (MAC) unit having protocols that are defined between the UE and the RNC to multiplex the user plane and control plane data. AS may further include a Physical Layer unit having protocols that are defined between the UE and the Node B to transfer data over the radio link. The interface between the UE and the RNC in the Physical Layer handles the macro diversity combining and dividing functions.
    [0032] Furthermore, NAS can employ the services provided by RRC (ie the upper layer of AS), such as an initial direct transfer procedure, a direct downlink transfer procedure, and an uplink transfer procedure. Here, the initial direct transfer procedure can be used to establish a signaling connection. It can also be used to port NAS messages through the radio interface. The downlink direct transfer procedure can be used in the downlink direction to carry the NAS messages through the radio interface. The uplink direct transfer procedure can be used in the uplink direction to carry NAS messages across the radio interface belonging to a signaling connection. In order for the direct downlink transfer procedure & direct uplink transfer procedure to work, a signaling connection, which can be established in the initial direct transfer procedure, can be kept in the RRC until it is not explicitly required to close by the NAS. Certain portions of this description will use protocols and terminology specific to 3GPP TS 25.331, v9.1.0 ("Radio Resource Control Protocol (RRC) Specification"), incorporated by reference herein in its entirety, to provide greater clarity of the details described here. However, those skilled in the art will understand that other protocols and standards can be used.
    [0033] The multiple access and modulation scheme employed by the access network 300 may vary depending on the particular telecommunications standard being developed. By way of example, the standard might include Optimized Data Evolution (EV-DO) or Ultra Mobile Broadband (UMB). EV-DO and UMB are air interface standards promulgated by the 3rd Partnership Project. Generation 2 (3GPP2) as part of the CDMA2000 family of standards and employs CDMA to provide broadband Internet access to mobile stations. The standard may alternatively be UTRA employing W-CDMA and other CDMA variations such as TD-SCDMA; GSM employing TDMA; and Evolved UTRA (E-UTRA), UMB, IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM employing OFDMA. UTRA, E-UTRA, UMTS, LTE and GSM are described in 3GPP organization documents. CDMA2000 and UMB are described in documents in the 3GPP2 organization documents. The actual wireless communication standard and multiple access technology employed will depend on the specific application and general design restrictions imposed on the system.
    [0034] Node B (eg 342) may have multiple antennas supporting MIMO technology. The use of MIMO technology allows Node B 342 to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity.
    [0035] Spatial multiplexing can be used to transmit different data streams simultaneously on the same frequency. Data streams may be transmitted to a single UE (eg 330) to increase the data rate or to multiple UEs (eg 330, 332) to increase overall system capacity. This is achieved by spatially precoding each data sequence and then transmitting each spatially precoded sequence through a different downlink transmit antenna. The spatially pre-coded data sequences arrive at UEs 330, 332 with different spatial signatures, which allows each of the UEs 330, 332 to retrieve one or more data sequences destined for that UE 330, 332. In uplink, each UE 330 transmits a spatially precoded data stream, which allows the Node B 342 to identify the source of each spatially precoded data stream.
    [0036] Spatial multiplexing is generally used when channel conditions are good. When channel conditions are less favorable, beamforming can be used to focus transmission energy in one or more directions. This can be achieved by spatially precoding data for transmission over multiple antennas. To achieve good coverage at cell edges, a single-sequence beamforming transmission can be used in combination with transmission diversity.
    [0037] Figure 4 is a block diagram of a Node B 410 in communication with a UE 450 in a RAN 400, where RAN 400 may be RAN 202 of figure 2, Node B 410 may be Node B 208 of Figure 2 and the UE 450 may be the UE 210 of Figure 2. In downlink communication, a transmission processor 420 may receive data from a data source 412 and control signals from a controller/processor 440. The transmission processor 420 provides various signal processing functions for control and data signals in addition to reference signals (eg pilot signals). For example, the 420 transmitter processor can provide Cyclic Redundancy Check (CRC) codes for error detection, encoding, and interleaving to facilitate forward error correction (FEC), mapping into signal constellations based on various schemes. modulation (eg, BPSK, QPSK, M-PSK, M-QAM, and the like), spreading with variable orthogonal spreading factors (OVSF), and multiplying with encryption codes to produce a series of symbols. Channel estimates from a channel processor 444 may be used by a controller/processor 440 to determine the encoding, modulation, spreading and/or encryption schemes for transmission processor 420. Such channel estimates may be derived from a signal reference transmitted by UE 450 or feedback contained in midamble 214 (FIG. 2) of UE 450. Symbols generated by transmit processor 420 are provided to a transmit frame processor 430 to create a frame structure. Transmit frame processor 430 creates this frame structure by multiplexing the symbols with a midamble 214 (FIG. 2) from controller/processor 440, resulting in a series of frames. The frames are then provided to a transmitter 432, which provides various signal conditioning functions including amplification, filtering, and modulation of the frames on a carrier for transmission downlink over the wireless medium via smart antennas 434. Smart antennas 434 can be implemented with bidirectional adaptive beam steering antenna assemblies or other similar beam technologies.
    [0038] At UE 450, a receiver 454 receives the downlink transmission through an antenna 452 and processes the transmission to retrieve the modulated information on the carrier. Information retrieved by receiver 454 is provided to a receive frame processor 460, which analyzes each frame, and provides midamble 214 (FIG. 2) to a channel processor 494 and data, control, and reference signals to a processor. 470. Receive processor 470 then reverses the processing performed by transmit processor 420 at Node B 410. More specifically, receive processor 470 decrypts and spreads the symbols and then determines the most likely signal constellation points transmitted by Node B 410 based on the modulation scheme. These soft decisions can be based on channel estimates computed by the 494 channel processor. The soft decisions are then coded and de-interleaved to retrieve data, control, and reference signals. The CRC codes are then checked to determine if the frames were successfully decoded. The data carried by the successfully decoded frames will then be supplied to a data store 472, which represents the applications running on the UE 450 and/or various user interfaces (eg monitor). The control signals carried by the successfully decoded frames will be provided to a 490 controller/processor. When frames are unsuccessfully decoded by the 470 receiver processor, the 490 controller/processor may also utilize an acknowledgment protocol (ACK) and /or negative acknowledgment (NACK) to support retransmission requests for these frames.
    [0039] In uplink, data from a data source 478 and control signals from the controller/processor 490 are provided to a transmission processor 480. The data source 478 can represent applications running on the UE 450 and various user interfaces ( eg keyboard). Similar to the functionality described with respect to downlink transmission by Node B 410, transmission processor 480 provides various signal processing functions, including CRC codes, encoding and interleaving to facilitate FEC, mapping to signal constellations, spreading with OVSFs, and encrypting to produce a series of symbols. Channel estimates, derived by the channel processor 494 from a reference signal transmitted by Node B 410 or from the feedback contained in the midamble transmitted by Node B 410, can be used to select encoding, modulation, spreading, and/or encryption schemes suitable. Symbols produced by transmit processor 480 will be provided to transmit frame processor 482 to create a frame structure. Transmit frame processor 482 creates this frame structure by multiplexing the symbols with a midamble 214 (Fig. 2) from controller/processor 490, resulting in a series of frames. Frames are then provided to a transmitter 456, which provides various signal conditioning functions including amplification, filtering, and modulation of frames on a carrier for uplink transmission over the wireless medium through antenna 452.
    [0040] The uplink transmission is processed at Node B 410 in a similar manner as described with respect to the receiver function at UE 450. A receiver 435 receives the uplink transmission through antenna 434 and processes the transmission to retrieve the modulated information in the carrier. The information retrieved by receiver 435 is provided to a receive frame processor 436, which analyzes each frame, and provides midamble 214 (FIG. 2) to channel processor 444 and data, control, and reference signals to a receive processor 438. Receive processor 438 performs inverse processing performed by transmission processor 480 at UE 450. The data and control signals carried by the successfully decoded frames can then be supplied to a data store 439 and the controller /processor, respectively. If some of the frames are unsuccessfully decoded by the receiving processor, controller/processor 440 may also use an ACK/NACK protocol to support retransmission requests for those frames.
    [0041] The controller/processor 440 and 490 can be used to direct the operation in the Node B 410 and the UE 450, respectively. For example, the 440 and 490 controller/processors can provide various functions including timing functions, peripheral interfaces, voltage regulation, power management, and other control functions. The computer readable media of memories 442 and 492 can store data and software for Node B 410 and UE 450, respectively. A scheduler/processor 446 at Node B 410 may be used to allocate the resources to the UEs and schedule downlink and/or uplink transmissions to the UEs.
    [0042] Fast dormancy is a feature for packet data users, generally supported by an RNC, that allows for a substantial reduction in the amount of time a UE needs to remain in an active state, thus improving lifetime of the battery. For example, live field test results indicate a timeout improvement of more than 100% in a UMTS device using fast dormancy to send the UE to idle on existing networks. Fast dormancy further frees up unused radio resources and moves the UE to an idle mode or a so-called "URA_PCH" state (defined in the 3GPP RRC protocol specification) so that the network can free up additional capacity that can be used for other users.
    [0043] In certain applications, although a UE may have completed its data transfer and does not expect further data exchange, the UE must expect the network to move it from the CELL-DCH or CELL_FACH state to idle mode or to CELL_PCH or URA_PCH state (each of these states is also defined in the 3GPP RRC protocol specification). This is because the network may not know if the UE has more data to transfer, and therefore may keep the UE in these data transfer states for a much longer period of time than necessary. The network does this to avoid additional setup delay for subsequent packet data transfers, in case there are actually more data packets to be transferred.
    [0044] In general, since a network may not be able to anticipate the data transfer characteristics of particular applications, this situation can lead to excessive battery drain. That is, the UE application tier usually autonomously determines whether it has any more data to exchange. By using application layer acknowledgment (for data transfer) and application-specific inactivity timers, the UE can reliably determine when it is appropriate to send an indication to the network indicating that the UE no longer needs this signaling connection, since the data transfer is complete, by including a cause value indicating the end of the data transfer session. Here, the fast dormancy feature allows the UE to send this indication to the network in an RRC Signaling Connection Release Indication (SCRI) message. In this way, the network can make an informed decision on how to handle this UE. That is, the network can decide to release the signaling connection, in which case it can then decide to release the RRC connection and let the UE go down. Alternatively, it can keep the UE in the CELL_PCH or URA_PCH state in order to achieve similar battery savings while ensuring faster reconfiguration for data transfer in the more distant future. Such behavior is described as fast dormancy, as the UE moves from active to inactive data transfer much faster than traditional waiting for inefficient inactivity timers to expire.
    [0045] Fig. 5 is a call flowchart 500 illustrating a problem with a prior art procedure for relocating a UE 502 from a source RNC (RNC-1) 54, which supports a fast dormancy feature, to a target RNC (RNC-2) 506, which does not support a fast sleep feature. That is, in this situation, the UE 502 and the target RNC 506 may lose synchronization with respect to the core network domain situation. In the process illustrated in Figure 5, five sequential phases are designed with numbers 1-5 on the left side of the illustration, where time moves forward in a descending direction as per the illustration. Although the illustration shows the communication taking place directly between the UE and the RNCs or the OS domain of the CN, those skilled in the art will understand that these arrows represent upper layer communication which is based on lower layer communication between other entities such as Node B, etc.
    [0046] In phase 1, the UE 502 establishes an RRC connection with RNC-1 504. Here, the UE 502 provides an RRC 510 connection request message to the RNC-1 404, for example using the uplink CCCH, including an initial UE identity and an establishment cause value, with a domain indicator set to indicate the OS domain. The RNC-1 404 may then respond with an RRC 512 connection setup message, for example, using the downlink CCCH, including the parameters necessary to establish the packet-swapped communication. In phase 2, with the RRC connection setup being complete, the UE 502 provides an initial direct handoff 514 to initiate a packet-switched call to the packet-switched domain of the core network 508.
    [0047] In step 3, the radio bearer reset (RB) message 516 is sent from the source RNC 504 to the UE 502, including an instruction to the UE 502 to reallocate an SRNS, served by the source RNC ( RNC-1) 504, for a target SRNS, served by the target RNC (RNC-2) 506. This reconfiguration/relocation may be requested due to a change in QoS, due to differences in the services available in the two SRNSs, or by any other proper reason. In several examples, a relocation procedure may be requested as a part of any one or more of the following RRC reset messages from source RNC 504: RADIO SUPPORT RESET (as illustrated, 516), PHYSICAL CHANNEL RESET, RELEASE RADIO SUPPORT CONFIGURATION, RADIO SUPPORT CONFIGURATION, TARNSPORT CHANNEL RECONFIG, CELL UPDATE CONFIRMATION, URA UPDATE CONFIRMATION, etc. Upon reconfiguration of the radio bearer and relocation of the UE 502 to the SRNS served by the target RNC 506, the UE 502 can provide a complete RB reconfiguration message 518 to the target RNC 506 indicating that the reconfiguration is performed.
    [0048] In phase 4, an application/entity in the UE 502 can become idle when no data traffic is exchanged between the UE 502 and the RNC 506. Accordingly, such state of no data exchange can be perceived in the UE 502 , in which case the app can turn off an active state and trigger a dormant state, power-saving state, or inactive state (for example, to save battery power). Accordingly, an indicator such as a message can be sent from the radio resource control layer in the UE 502 to the RNC 506.
    [0049] In step 5, the UE 502 provides a SCRI message 520. The SCRI message 520 can be used by the UE 502 to request the network to initiate a state transition to a dormant, inactive state or essentially any RRC efficient state such as CELL_PCH or URA_PCH. Unfortunately, as described, a radio link failure occurs thereafter with respect to RNC 506 as RNC 506 does not support a fast sleep feature. In this way, the UE 502 and the RNC 506 become out of sync after the relocation, and in step 6, the behavior in the UE 502 becomes unknown to the network. That is, the OS domain of core network 508 is open with respect to UE 502, and is closed with respect to RNC 506. The current information in the message as described below does not solve such problems.
    [0050] For example, a timer T323 can be maintained in the UE 502 in addition to the RNC 506. Here, the timer T323 can be a timer to manage the release of a signaling connection and termination of a packet exchanged data session . Those skilled in the art will be familiar with the T323 timer as defined in the RRC UMTS TS 25.331 protocol specification. In a legacy RNC that does not support fast dormancy, the expiration of timer T323 can be used to trigger a low power mode on the UE and a release of the radio resources assigned to that UE. Prior to step 3 in Figure 5, that is, prior to reallocation of the radio bearer, the UE retains a valid value of timer T323 stored in an information element (IE) called "UE timers and constants in connected mode" in the variable TIMERS_AND_CONSTANTS of system information block (SIB) type 1. In step 4 of figure 5, that is, after radio bearer relocation, when the application triggers the fast sleep feature, the UE 502 will still be under the impression that the "new" cell, corresponding to RNC-2 506, has the characteristic of rapid dormancy, while in reality it does not.
    [0051] That is, in order to indicate the fast dormancy characteristic the UE 502 conventionally reuses an existing RRC message called SCRI with a new cause. However, UE 502 generally does not close the packet-swapped domain of core network 508 of ESTABLISHED_SIGNALING_CONNECTIONS (i.e., a variable used to store information about the established signaling connections including a signaling connection list).
    [0052] On the other hand, the SCRI message and procedure are conventionally used by the UE 502 to indicate to the UTRAN that one of its signaling connections has been released. This procedure can, in turn, initiate an RRC connection release procedure. Thus, when the RNC (RNC-2) 506 does not support the fast dormancy feature, it fails to recognize the different cause of the SCRI message, and can release the connection to the packet-switched domain of the core network 508.
    [0053] Thus, it is observed that the UE 502 and the RNC 506 fall out of sync in a conventional way with respect to the open situation of the packet-swapped domain as a consequence of the relocation of the RNC-1 504, which supports the fast dormancy feature , for the RNC-2 506, which does not support the fast sleep feature. Subsequent packet-switched calls or packet-switched signaling messages from the UE 502 can then be dropped by the network, interrupting the NAS layer functionality.
    [0054] Thus, in one aspect of the present description, an open situation of a packet-switched domain of a core network is synchronized in a UE and in an RNC when the SRNS reallocation occurs while a fast dormancy feature is active. In one example, in any SRNS reallocation, the UE can always assume that the target RNC does not support the fast dormancy feature, and thus the UE can disable the fast dormancy feature in the SRNS reallocation. In this way, even though the UE does not know if the new RNC supports this feature, the potential loss of synchronization can be avoided. However, the disadvantage of this approach is that it disables the fast dormancy feature even in a situation where it can be supported, where the UE may not indicate to the target RNC that it does not have any data to be sent uplink, resulting in a view Shortened battery life in EU.
    [0055] In another approach according to the present description, the situation of the packet-switched domain of the core network to be synchronized by the exchange of reconfiguration messages between the UE and the target RNC, where timers are employed to preserve synchronization of UE/network, and while a UE application triggered the UE's dormancy. In one example, timer value T323 can be ported in reset messages in order to support synchronization.
    [0056] In one aspect of the description, each type of reset message (for example, RADIO SUPPORT RESET, PHYSICAL CHANNEL RESET, RADIO SUPPORT RELEASE, RADIO SUPPORT SETUP, TRANSPORT CHANNEL RESET, CONFIRMATION messages CELL UPDATE, and UPDATE CONFIRMATION URA) sent from an RNC to the UE can carry an IE corresponding to the timer value T323 when a network supports the fast sleep feature. Thus, in the case of an SRNS reallocation, a source RNC 504 can communicate with a UE 502 that a target RNC 506 to which the UE 502 is to reallocate either supports the fast dormancy feature or not. Here, the source RNC 504 and the target RNC 506 may include a communication interface in a return access channel connection, for example, being a direct link between the target and source RNCs, or a connection through an intermediary, by example, on the core network. However, since some reconfiguration messages from an RNC are used by the network to exchange several configurations within the same cell, some of the IEs corresponding to the timer value T323 will be unnecessarily broadcast through the air interface when the network supports the fast dormancy feature . This approach may therefore increase the overhead of the number of bits transmitted over the air interface and may require communication via the return access channel between the RNCs.
    [0057] In another aspect of the description, when the network supports the fast dormancy feature, each type of reconfiguration message sent from an RNC to the UE can carry an IE corresponding to the timer value T323 when the timer value T323 was changed; when the T323 timer value has not changed, but the network supports the fast sleep feature, each type of reset message can carry a simple indication, such as a single bit, to indicate that the network supports the fast sleep feature. In this way, the amount of overhead transmission can be reduced when compared to IE transmission corresponding to the T323 timer value. However, once again, since reset messages are used by the network for multiple types of reset within the same cell, unnecessary overhead can still occur when the T323 value has been changed even though an SRNS reallocation is not required.
    [0058] In another aspect of the description, reset messages requesting an SRNS relocation to a target RNC that supports the fast sleep feature may carry the IE corresponding to the T323 timer value when the T323 timer value has been changed, when the timer value T323 is not changed, but the target RNC supports the fast sleep feature the reset message can include a simple indication such as a single bit to indicate that the target RNC supports the fast sleep feature. In this way, the unnecessary overhead in broadcasting the IE corresponding to the T323 timer value in each reset message (that is, messages even where an SRNS reallocation is not being requested) can be substantially reduced. Furthermore, even in a case where an SRNS reallocation is being requested, the overhead transmission overhead can be reduced when the timer value T323 is not changed, by virtue of transmitting only the simple indication instead of the IE corresponding to the timer value T323. However, in order to determine whether the timer value T323 has not been changed, and thus to determine whether to transmit the IE corresponding to the timer value T323 or the simple indication to indicate that the target RNC supports the dormancy characteristic Fast, the source RNC 504 and the target RNC 506 may require the communication of the timer value T323 via a reverse access channel connection. Such communication of the T323 timer value can be difficult to implement in existing networks.
    [0059] In another aspect of the description, reset messages that request an SRNS reallocation to a target RNC that supports the fast sleep feature can carry the IE corresponding to the T323 timer value. Here, the UE can interpret the presence of the IE corresponding to the timer value T323 as an indication that the target RNC for which an SRNS reallocation is to take place supports the fast dormancy feature. That is, if a reset message that is requesting an SRNS reallocation does not include the IE corresponding to the timer value T323, then the UE will understand this as an indication that the target RNC on which the SRNS reallocation is to take place does not support the feature of fast numbness. In that case, the UE can handle the signaling with the target RNC following the SRNS reallocation as a legacy RNC, and can suitably maintain the synchronization of the situation of the packet-swapped domain of the core network. According to this aspect of the description, coordination between RNCs regarding the value of timer T323 is not necessary.
    [0060] Fig. 6 is a flowchart illustrating a process of reallocating a UE from a source RNC to a target RNC in accordance with an aspect of the present description. In some aspects of the description, the process may be performed by the circuitry or a processor as illustrated in Figure 1. In some aspects of the description the process may be performed by a combination of a plurality of RNCs 206 and a UE 210 as illustrated in figure 2. In some aspects of the description parts of the process may be performed by the UE 450 of figure 4. In some aspects of the description, the process may be performed by the UE and RNC illustrated in figure 7, described below. At block 602, the process sends a first reconfiguration message from a first RNC to a UE. Here, the first reconfiguration message is used by the network to change a UE configuration without UE relocation. For example, the first reset message might be a PHYSICAL CHANNEL RESET message. At block 604, the process resets the UE in response to the first reset message.
    [0061] In block 606, the process sends a second reconfiguration message from the first RNC to the UE. Here, the second reconfiguration message includes a notification to the UE which is about to undergo a SRNS reallocation from a first SRNS corresponding to the first RNC, to a second SRNS corresponding to a second RNC (target). For example, as illustrated in Figure 5, the second reset message may be a RADIO SUPPORT RESET message. However, as discussed above other reconfiguration messages may include notification to the UE that it is about to undergo SRNS reallocation.
    [0062] In block 608, the process determines in the UE whether the second target RNC corresponding to the target SRNS supports a fast dormancy feature. Here, the UE can determine whether the target RNC supports the fast sleep feature by observing an indicator within the second reconfiguration message received from the first source RNC, that the target RNC supports the fast sleep feature. As discussed above, the indicator may be a single bit within the second reset message designated for that purpose; the indicator can be an information element corresponding to the timer value T323; or any other suitable indicator to indicate that the target RNC supports the fast dormancy characteristic. If the second reset message indicates that the target RNC supports the fast sleep feature, then the process moves to block 610; otherwise, if the second reset message does not indicate that the target RNC supports the fast sleep feature, then the process moves to block 616.
    [0063] In block 610, the process performs an SRNS reallocation, where the UE undergoes a reallocation from the source SRNS corresponding to the source RNC, to the target SRNS corresponding to the target RNC. Since the target RNC supports the fast dormancy feature, the UE is aware of this situation due to the notification received by the UE in the second reconfiguration message, the UE may enter a dormant state when it is determined that there is an absence of data to be transferred from the UE to the network. For example, as described above, an application or entity in the UE can detect such a condition and trigger the dormant state, such as an idle state in the UE. In that case, the process moves to block 612, where the UE provides a SCRI message including an indication that the UE will enter the dormant state for the second target RNC. Then, at block 614, the UE enters the dormant state, such as the idle state, the CELL_PCH or URA_PCH state, or any suitable battery saving state. The process is then closed.
    [0064] Returning to block 616, the process determined in block 608 that the target RNC does not support the fast sleep feature, that is, the target RNC can be a legacy RNC. Thus, in block 616, the process relocates the UE from the source RNC to the target RNC as instructed. However, in block 618, the process undergoes the legacy operation of the UE and target RNC, without using the fast dormancy feature. For example, with the legacy operation, when the target RNC receives a SCRI message from the UE, if the IE "Signaling Connection Release Indication Cause" is not included in the SCRI message, the target RNC can request the connection release signage. On the other hand, if the IE "Signaling Connection Release Indication Cause" is included in the UE SCRI message, the target RNC can initiate a state transition to efficient battery saving state, INACTIVE, CELL_PCH, URA_PCH or CELL_FACH. In this way, the UE maintains synchronization with the packet-swapped core network even though an SRNS reallocation occurs for an RNC that does not support the fast dormancy feature.
    [0065] Fig. 7 is a conceptual block diagram of a UE 702 and an RNC 704 according to an aspect of the present description. Here, the UE 702 and the RNC 704 each include various electronic components for performing certain functions. For example, the UE 702 includes an electronic component 706 for receiving an SRNS relocation message, for example, from a source RNC and an electronic component 708 for determining whether a SRNS, for example, the target SRNS to which the UE 702 has been instructed to relocate, supports a fast sleep feature. The UE 702 further includes an electronic component 710 for providing a SCRI message, for example, including an indication that the UE will enter a dormant state; an electronic component 712 for detecting the absence of data for transfer to an RNC; and an electronic component 714 for entering the dormant state. The RNC 704 includes an electronic component 716 for receiving a SCRI message from a UE and an electronic component 718 for providing a reset message to a UE. Optionally, the RNC 704 can additionally include electronic components within the dashed box 720. That is, the RNC 704 can include an electronic component 722 to support a fast sleep feature and an electronic component 724 to receive an indication that a UE has the which has connection will enter a dormant state.
    [0066] Various aspects of a telecommunications system have been presented with reference to a W-CDMA system. As those skilled in the art will readily appreciate, several aspects described throughout this description can be extended to other telecommunication systems, network architectures, and communication standards. By way of example, various aspects can be extended to other UMTS systems such as TD-SCDMA, High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+) and TD-CDMA. Various aspects can also be extended to systems employing Long Term Evolution (LTE) (in FDD, TDD or both modes), LTE-Advanced (LTE-A) (in FDD, TDD or both modes), CDMA2000, EV- DO, UMB, IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, UWB, Bluetooth, and/or other suitable systems. The actual telecommunication pattern, network architecture, and/or communication pattern employed will depend on the specific application and general design constraints imposed on the system.
    [0067] Various processors have been described with respect to various equipment and methods. These processors can be implemented using computer software, various electrical components such as electronic hardware, or any combination thereof. Whether such processors are implemented as hardware or software will depend on the particular application and overall design constraints. By way of example, a processor, any part of a processor, or any combination of processors, presented in this description can be implemented with a microprocessor, microcontroller, DSP, FPGA, PLD, a situation machine, gated logic, hardware circuits discrete and other suitable processing components configured to perform the various functions described throughout this description. The functionality of a processor, any part of a processor, or any combination of processors shown in this description can be implemented with software running by a microprocessor, microcontroller, DSP, or other suitable platform.
    [0068] In one or more aspects of the description, the described functions may be implemented in hardware, software, firmware or any combination thereof. If implemented in software, functions can be stored in or transmitted as one or more instructions or code in a computer-readable medium. Computer-readable media may be transient or non-transient, and may include both computer storage media and communication media including any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available media that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, such non-transient computer readable media may comprise RAM, ROM, EEPROM, CD-ROM or any other optical disk storage, magnetic disk storage or other program code devices or any other means that can be used to carry or store desired program code media in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly called a computer-readable medium. For example, if the software is transmitted from a network site, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave, so coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are transient entities included in the definition of medium. Floppy disk and disk, as used herein, include compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk, and blu-ray disk where floppy disks normally reproduce data magnetically, while disks reproduce data optically. with lasers. Combinations of the above must also be included within the scope of computer readable media. Computer-readable media can be embodied in a computer program product. By way of example, but not limitation, a switch program product can include a computer-readable medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this description depending on the particular application and general design constraints imposed on the system as a whole.
    [0069] It should be understood that the specific order or hierarchy of steps in the described methods is an illustration of the illustrative processes. Based on design preferences, it is understood that the specific order or hierarchy of steps in methods can be rearranged. The method claims the present elements of the various steps in an illustrative order and is not to be limited to the specific order or hierarchy presented unless specifically mentioned herein.
    [0070] The foregoing description is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, claims should not be limited to the aspects illustrated here, but the full scope consistent with the language of claims should be agreed, where reference to a singular element should not mean "one and only one" unless specifically mentioned, but instead "one or more". Unless specifically noted otherwise, the term "some" refers to one or more. A phrase referring to "at least one of" a list of items refers to any combination of those items, including unique elements. As an example, "at least one of: a, b or c" must cover: a; B; ç; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalences of elements of various aspects described throughout this description that are known or will be known later to those skilled in the art are expressly incorporated herein by reference and are to be encompassed by the claims. Furthermore, nothing described here should be dedicated to the public regardless of whether such description is explicitly recited in the claims. No claim element shall be considered under the provisions of 35 USC § 112, paragraph six, unless the element is expressly recited using the phrase "means to", or, in the case of a method claim, the element is recited using the phrase "step to".
    权利要求:
    Claims (7)
    [0001]
    1. Method (600) for wireless communication in a user equipment, UE, (502, 702), CHARACTERIZED by comprising: receiving (606), from a Server Radio Network Subsystem, SRNS, source, a notification relocation from the source SNRS to a target SRNS; determining (608), based on the received notification, whether a target Radio Network Controller, RNC, corresponding to the target SRNS supports a fast dormancy feature; submit (610) SRNS reallocation from the source SNRS to the target SRNS; providing (612) an indication, in a signaling connection release indication message, SCRI, to the target RNC that it will enter a dormant state; and entering (614) a dormant state when it is determined that there is no data to transfer from the UE to the network, if fast sleep feature support in the target RNC is determined.
    [0002]
    The method of claim 1, CHARACTERIZED by determining whether the target RNC corresponding to the target SRNS supports the fast sleep feature comprises determining whether a reconfiguration message received from the source SRNS includes an indicator to indicate that the target RNC supports fast dormancy feature.
    [0003]
    A method according to claim 1, characterized in that determining whether the target RNC corresponding to the target SRNS supports the fast sleep feature comprises determining whether a reconfiguration message received from the source SRNS includes an information element corresponding to a timer of dormancy, whose expiration triggers a low power mode in the UE.
    [0004]
    The method of claim 1, further comprising: disabling the fast dormancy feature, if the notification to relocate from the source SRNS to the target SRNS does not indicate support for the fast dormancy feature in the target RNC.
    [0005]
    5. Apparatus for wireless communication in a user equipment CHARACTERIZED by comprising mechanisms for carrying out a method as defined in any one of claims 1 to 4.
    [0006]
    Apparatus according to claim 5, characterized in that the mechanisms comprise at least one processor and a memory coupled to the at least one processor.
    [0007]
    7. Memory characterized by comprising instructions to cause a computer or processor to perform a method as defined in any one of claims 1 to 4.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112012003056B1|2021-04-20|systems and methods for maintaining core network state during relocation of server radio network subsystem
    KR20190129102A|2019-11-19|User Plane Relocation Technologies in Wireless Communication Systems
    ES2699465T3|2019-02-11|Mobility in a multi-point HSDPA communication network
    US9253809B2|2016-02-02|Apparatus and methods for improved user equipment | capability signaling
    CN109041222B|2020-02-14|Method and apparatus for intelligent random access procedure in telecommunications network
    US9292077B2|2016-03-22|Methods and apparatus for efficient service layer assistance for modem sleep operations
    BR112016010363A2|2020-08-18|APPLIANCE AND METHODS TO EXECUTE EXTERNAL LOOP POWER CONTROL FOR PREMATURE FRAME TERMINATION IN WIRELESS COMMUNICATIONS
    US20150365856A1|2015-12-17|Managing radio resource control | state transitions at a user equipment
    US9706451B2|2017-07-11|Method and apparatus for pre-configuring for a serving cell change to neighbor cells
    KR20140041832A|2014-04-04|Apparatus and method for maintaining a circuit-switched voice call in a multi-rab wireless communication system in an area of weak coverage
    US9768910B2|2017-09-19|Event 6D enhancements
    JP6362706B2|2018-07-25|Apparatus and method for triggering a maximum power reporting event in a wireless communication network
    EP2929731B1|2020-09-23|Apparatus and method for enhanced mobile power management
    US9237564B2|2016-01-12|Enhanced reconfiguration procedure at a mobile terminal to reduce signaling and power consumption overhead
    US20120108182A1|2012-05-03|Receiving a message identifying neighbor cells
    BRPI1012995B1|2021-07-06|METHOD, MOBILE STATION AND BASE STATION TO PROVIDE AN INDICATOR OF THE PRESENCE OF A FIRST ACCESS NETWORK THAT IS CAPABLE OF INTEROPERATING WITH A SECOND ACCESS NETWORK
    US20220015001A1|2022-01-13|Improved Techniques for Conditional Handover and Bi-Casting
    WO2014169849A1|2014-10-23|Method for realizing ue measurement, equipment and computer storage medium
    同族专利:
    公开号 | 公开日
    BR112012003056A2|2016-08-02|
    KR101364654B1|2014-02-19|
    TW201119436A|2011-06-01|
    TWI450607B|2014-08-21|
    HUE035879T2|2018-05-28|
    CN104469863B|2018-04-10|
    CN102474769B|2015-12-09|
    US20110038347A1|2011-02-17|
    EP2465288A1|2012-06-20|
    EP2465288B1|2017-06-07|
    US8638711B2|2014-01-28|
    ES2639415T3|2017-10-26|
    JP2013502164A|2013-01-17|
    JP2014140201A|2014-07-31|
    KR20120043084A|2012-05-03|
    JP5749365B2|2015-07-15|
    WO2011019832A1|2011-02-17|
    JP5583768B2|2014-09-03|
    CN102474769A|2012-05-23|
    CN104469863A|2015-03-25|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    DE10105093A1|2001-02-05|2002-08-08|Nokia Corp|Paging method and system for a radio access network|
    US7068636B2|2002-06-21|2006-06-27|Asustek Computer Inc.|Method for determining RLC entity re-establishment during SRNS relocation|
    AU2006267255B2|2005-07-07|2010-03-04|Nokia Technologies Oy|Handover method and apparatus between different systems|
    DE202005021930U1|2005-08-01|2011-08-08|Corning Cable Systems Llc|Fiber optic decoupling cables and pre-connected assemblies with toning parts|
    US8265034B2|2006-05-17|2012-09-11|Research In Motion Limited|Method and system for a signaling connection release indication|
    WO2008096685A1|2007-02-05|2008-08-14|Nec Corporation|Base station-to-base station handover method, wireless communication system, drx control method, base station, and communication terminal|
    US8693409B2|2007-08-10|2014-04-08|Interdigital Patent Holdings, Inc.|Method and apparatus for supporting paging over an HS-DSCH in CELL—PCH and URA—PCH states|
    EP2387283B1|2007-11-13|2018-11-28|BlackBerry Limited|Method and apparatus for state/mode transitioning|
    WO2009104086A1|2008-02-22|2009-08-27|Nokia Corporation|Mobile equipment autonomous quick release detection|EP2247146B1|2005-12-14|2011-11-16|Research In Motion Limited|Method and apparatus for user equipment directed radio resource control in a UMTS network|
    ES2353609T3|2006-05-17|2011-03-03|Research In Motion Limited|METHOD AND SYSTEM FOR INDICATION OF SIGNALING CONNECTION RELEASE IN A UMTS NETWORK.|
    US20080049662A1|2006-08-25|2008-02-28|Research In Motion Limited|Apparatus, and associated method, for releasing a data-service radio resource allocated to a data-service-capable mobile node|
    US8085714B2|2007-09-29|2011-12-27|Jaakko Johannes Sitomaniemi|Method, apparatus and computer program product for preserving a signalling connection|
    EP2387283B1|2007-11-13|2018-11-28|BlackBerry Limited|Method and apparatus for state/mode transitioning|
    EP2356878B1|2008-11-10|2015-07-29|BlackBerry Limited|Method and apparatus of transition to a battery efficient state or configuration by indicating end of data transmission in long term evolution|
    WO2011025284A2|2009-08-26|2011-03-03|Samsung Electronics Co., Ltd.|Method and system to handle a signaling connection release process in a wireless communication system|
    AU2010320843B2|2009-11-23|2014-07-10|Blackberry Limited|Method and apparatus for state/mode transitioning|
    ES2805149T3|2009-11-23|2021-02-10|Blackberry Ltd|State or mode transition trigger based on the transmission of a connection release signaling indication message|
    AU2010321204B2|2009-11-23|2014-11-20|Blackberry Limited|Method and apparatus for state/mode transitioning|
    MX2012005874A|2009-11-24|2012-11-30|Research In Motion Ltd|Method and apparatus for state/mode transitioning.|
    US8983532B2|2009-12-30|2015-03-17|Blackberry Limited|Method and system for a wireless communication device to adopt varied functionalities based on different communication systems by specific protocol messages|
    CN102783241A|2010-02-10|2012-11-14|捷讯研究有限公司|Method and apparatus for state/mode transitioning|
    KR101691482B1|2010-10-15|2016-12-30|삼성전자주식회사|Portable Device For Adaptive Data Communication Control And Method thereof|
    US9167618B2|2010-11-16|2015-10-20|At&T Mobility Ii Llc|Data bundling and fast dormancy based upon intelligent application learning|
    CN102469446B|2010-11-19|2014-08-20|华为技术有限公司|Method and device for business processing|
    WO2012132165A1|2011-03-29|2012-10-04|Ｎｅｃカシオモバイルコミュニケーションズ株式会社|Communication device, communication system, communication method, and program|
    SG194059A1|2011-04-01|2013-11-29|Interdigital Patent Holdings|Method and apparatus for controlling connectivity to a network|
    EP3570628B1|2011-08-12|2020-12-30|BlackBerry Limited|Handling a connection in a wireless communication system|
    US9258839B2|2011-08-12|2016-02-09|Blackberry Limited|Other network component receiving RRC configuration information from eNB|
    US9001714B2|2011-09-06|2015-04-07|Broadcom Corporation|Ethernet physical layer device using time division duplex|
    EP2777358B1|2011-11-11|2018-01-10|BlackBerry Limited|Method and apparatus for user equipment state transition|
    CN102413516B|2011-12-23|2014-03-12|大唐移动通信设备有限公司|Method and equipment for releasing wireless signaling bearing resources|
    EP2611257B1|2011-12-27|2016-08-03|Telefonaktiebolaget LM Ericsson |Method and device for increasing performance in a radio communication system|
    WO2013119021A1|2012-02-06|2013-08-15|삼성전자 주식회사|Method and apparatus for activating sleep mode of terminal|
    CN103297211B|2012-02-29|2016-01-20|华为技术有限公司|The method for building up of independent uplink high-speed special physical control channel and device|
    US9155121B2|2012-03-27|2015-10-06|Blackberry Limited|Re-establishment of suspended RRC connection at a different eNB|
    US9295095B2|2012-03-27|2016-03-22|Blackberry Limited|UE preference indicator for suspension|
    US9247575B2|2012-03-27|2016-01-26|Blackberry Limited|eNB storing RRC configuration information at another network component|
    GB2501931A|2012-05-11|2013-11-13|Renesas Mobile Corp|Wireless devices and apparatus and computer programs therefor|
    CN103428762A|2012-05-22|2013-12-04|中兴通讯股份有限公司|Radio resource management method, RNC and UE|
    US9781767B2|2012-08-24|2017-10-03|Samsung Electronics Co., Ltd.|Method for achieving fast dormancy of user equipmentin Cell—PCH or URA—PCH state in UMTS|
    US9942802B2|2013-02-21|2018-04-10|Lg Electronics Inc.|Common configuration-based operating method in wireless communication system and apparatus supporting same|
    JP6266770B2|2013-10-25|2018-01-24|クアルコム，インコーポレイテッド|Selective ignore of RLC errors during handover|
    US20150119038A1|2013-10-30|2015-04-30|Qualcomm Incorporated|Method and apparatus for cell reselection during serving radio network subsystemrelocation|
    CN104853450A|2014-01-27|2015-08-19|马维尔国际有限公司|Method and equipment for processing packet switching service|
    CN105592534B|2014-11-07|2019-03-29|思科技术公司|For providing the system and method for battery saving mode enhancing in a network environment|
    WO2020050754A1|2018-09-03|2020-03-12|Telefonaktiebolaget Lm Ericsson |Relocation of a user equipment connection from a source radio network controller rnc to a target rnc initiated via a core network|
    法律状态:
    2018-03-27| B15K| Others concerning applications: alteration of classification|Ipc: H04W 36/00 (2009.01), H04W 36/10 (2009.01) |
    2019-01-15| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|
    2019-12-17| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2021-02-02| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2021-04-20| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 10 (DEZ) ANOS CONTADOS A PARTIR DE 20/04/2021, OBSERVADAS AS CONDICOES LEGAIS. |
    优先权:
    申请号 | 申请日 | 专利标题
    US23304309P| true| 2009-08-11|2009-08-11|
    US61/233,043|2009-08-11|
    US12/853,937|2010-08-10|
    US12/853,937|US8638711B2|2009-08-11|2010-08-10|Systems and methods of maintaining core network status during serving radio network subsystem relocation|
    PCT/US2010/045192|WO2011019832A1|2009-08-11|2010-08-11|Systems and methods of maintaining core network status during serving radio network subsystem relocation|
    [返回顶部]